Buffer status reporting in a communications network

ABSTRACT

A technology that is operable to communicate buffer status report (BSR) information to an evolved node B (eNode B) is disclosed. In one embodiment, a user equipment is configured with circuitry configured to buffer data at the UE for communication to at least one of a master eNode B (MeNode B) or a secondary eNode B (SeNode B). BSR information is determined based on the buffered data at the UE. An uplink split configuration of the UE is determined for the MeNode B and the SeNode B. The MeNode B or the SeNode B is identified based on the uplink split configuration to send selected BSR information. The selected BSR information is communicated to the identified MeNode B or the selected SeNode B.

RELATED APPLICATIONS

This application claims the benefit of and hereby incorporates by reference U.S. Provisional Patent Application Ser. No. 61/898,425, filed Oct. 31, 2013, with an attorney docket number P61993Z.

BACKGROUND

In a typical communications network, an evolved node B (eNode B) is responsible for uplink (UL) quality of service (QoS) management. To manage the QoS of a user equipment (UE), the eNode B uses information received from the UE indicating which radio bearers (RBs) will require UL resources and the amount of resources each RB will need.

A dual connected UE can send uplink data to both a master eNode B (MeNode B) and a secondary eNode B (SeNode B). For a dual connected UE, UL traffic on a RB can be split between the MeNode B and the SeNode B at a packet data convergence protocol (PDCP) layer. For UL bearer split traffic, the UE can have two radio link control (RLC) buffers at the UE, e.g. one RLC buffer for the MeNode B and one RLC buffer for the SeNode B. The UE can measure a total size of the RLC buffer for the MeNode B and a total size of the RLC buffer for the SeNode B and can send a total buffer size of the RLC buffers to the MeNode B. However, a total buffer size does not indicate to the MeNode B an amount of UL resources (UL grant) to allocate in an MeNode B cell and an amount of UL resources to allocate in an SeNode B cell.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:

FIG. 1 depicts a dual connectivity user equipment (UE) in an uplink (UL) buffer status report (BSR) communication scheme in accordance with an example;

FIG. 2 depicts a flowchart to illustrate the functionality of the circuitry with a UE operable to determine when to send a BSR to one evolved node B (eNode B) or a plurality of eNode Bs in accordance with an example;

FIG. 3A depicts a dual short BSR with a truncated BSR media access control (MAC) control element (CE) in accordance with an example;

FIG. 3B depicts a dual long BSR with a full BSR MAC CE in accordance with an example;

FIG. 4 illustrates an R/R/E/logical channel identification (LCID) MAC subheader in accordance with an example;

FIG. 5 depicts the functionality of circuitry of a UE operable to communicate BSR information to an eNode B in accordance with an example;

FIG. 6 depicts the functionality of circuitry of a eNode B operable to communicate a BSR to another eNode B in accordance with an example;

FIG. 7 depicts a product including a non-transitory storage medium having stored thereon instructions that are adapted to be executed to implement a method of directing BSR information to an eNode B in accordance with an example; and

FIG. 8 illustrates a diagram of a UE in accordance with an example.

Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended.

DETAILED DESCRIPTION

Before the present invention is disclosed and described, it is to be understood that this invention is not limited to the particular structures, process steps, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating steps and operations and do not necessarily indicate a particular order or sequence.

An evolved node B (eNode B) can manage an uplink (UL) quality of service (QoS) of a user equipment (UE) in a communications network. To manage the QoS of the UE, the eNode B can use information from the UE indicating which radio bearers (RBs) will require UL resources and an amount of resources each RB will require. A radio bearer is an information communication path between an eNode B and a UE, e.g. packet flow path, with defined criteria such as a QoS level, data capacity level, a delay rate, a bit error rate, and so forth. In a communications network, various types or levels of bearers with different configurations can be established.

In one embodiment, the communications network can be a cellular network. The cellular network can be configured to operate based on a cellular standard, such as the third generation partnership projection (3GPP) long term evolution (LTE) Rel. 8, 9, 10, 11, or 12 standard, or the institute of electronic and electrical engineers (IEEE) 802.16p, 802.16n, 802.16m-2011, 802.16h-2010, 802.16j-2009, or 802.16-2009 standard.

In another embodiment, the communications network can be a wireless local area network (such as a wireless fidelity network (Wi-Fi)) that can be configured to operate using a standard such as the IEEE 802.11-2012, IEEE 802.11ac, or IEEE 802.11ad standard. In another embodiment, the communications network can be configured to operate using a Bluetooth standard such as Bluetooth v1.0, Bluetooth v2.0, Bluetooth v3.0, or Bluetooth v4.0. In another embodiment, the communications network can be configured to operate using a ZigBee standard, such as the IEEE 802.15.4-2003 (ZigBee 2003), IEEE 802.15.4-2006 (ZigBee 2006), or IEEE 802.15.4-2007 (ZigBee Pro) standard.

The UE can communicate UL resource requirements to the eNode B using buffer status report (BSR) information of the UE. The BSR information can indicate an amount of data that has been buffered by the UE for transmission on a radio bearer to one or more eNode Bs. The one or more eNode Bs can use the BSR information to allocate and schedule UL resources for the UE to maintain a selected QoS.

A dual connected UE in a communications network can send uplink (UL) data to a master evolved node B (MeNode B) and a secondary eNode B (SeNode B). In one embodiment, the UL data traffic on a bearer can be split at packet data convergence protocol (PDCP) layer between the MeNode B and SeNode B. For UL bearer split traffic, the UE can have two radio link control (RLC) buffers UE, e.g. one RLC buffer for the MeNode B and one RLC buffer for the SeNode B. Traditionally, the UE can measure a total size of the RLC buffer for the MeNode B and the RLC buffer for the SeNode B and can send a total buffer size of the RLC buffers to the MeNode B. In one embodiment, the UE can send the total buffer size of the RLC buffers directly to the MeNode B. In another embodiment, the UE can send the total buffer size of the RLC buffers indirectly to the MeNode B via the SeNode B. However, a total buffer size does not indicate to the MeNode B an amount of UL resources (UL grant) to allocate in an MeNode B cell and an amount of UL resources to allocate in SeNode B cell.

In a traditional communications network, the MeNode B can include a MAC scheduler to determine an UL grant for a UE based on: a BSR of the UE, channel conditions of the UE, and loading of the MeNode B/network. In one embodiment, for a communications network with a UE configured to use dual connectivity, the MeNode B and the SeNode B can each have MAC schedulers for a split bearer.

In one example, the MAC schedulers of the MeNode B and the SeNode B can communicate the BSR information of the UE, the channel conditions of the UE, and/or the loading information of the eNode Bs (MeNode B and SeNode B) between the MeNode B and the SeNode B to determine UL resource grants by the MeNode B and the SeNode B. For example, a BSR can be used for UL grant scheduling for UEs communicating buffered data to one or more eNode Bs.

In one embodiment, the BSR can contain information of the total size of RLC buffers and/or PDCP buffers of a UE. In another embodiment, the channel conditions of the UE can include channel quality indicator (CQI) information. In one example, the CQI information, loading information of the eNode Bs, and UL grant information by an MeNode B or an SeNode B can be communicated between the MeNode B and the SeNode B using an Xn interface.

FIG. 1 depicts a dual connectivity UE 110 in a UL BSR communication scheme 100. In one embodiment, the dual connectivity UE 110 can communicate a BSR message to an eNode B 120 and/or an eNode B 130. In another embodiment, the dual connectivity UE 110 can receive UL grant information from the eNode B 120 and/or the eNode B 130. In one example, the eNode B 120 can be an MeNode B and the eNode B 130 can be an SeNode B. In one configuration of the UL BSR communication scheme 100, the eNode B 120 or the eNode B 130 can communicate UL grant information, CQI information, BSR information, and/or loading information of the eNode B 130 or the eNode B 120, respectively. In one embodiment, the eNode B 120 and the eNode B 130 can communicate information using an Xn interface.

In one configuration, the dual connectivity UE 110 can send a BSR with separate buffer status information for the eNode B 120 and the eNode B 130. For example, the dual connectivity UE 110 can send separate buffer status information for the MeNode B and for the SeNode B in a common BSR message. In one example, when a total BSR is 100 bytes (BSR_Total), the UE can send a common BSR message indicating a 40 byte request (BSR_MeNode B) to the MeNode B and a 60 byte request (BSR_SeNode B) to the SeNode B. In one embodiment, the dual connectivity UE 110 can send the common BSR message to the eNode B 120, e.g. the MeNode B, and the eNode B 120 can relay the common BSR message to the eNode B 130, e.g. the SeNode B.

In another embodiment, the dual connectivity UE 110 can send the common BSR message to the eNode B 130, e.g. the SeNode B, and the eNode B 130 can relay the common BSR message to the eNode B 120, e.g. the MeNode B. In one example the eNode B 120 or 130 can relay the common BSR message to the other eNode B 130 or 120, respectively, via an Xn interface (such as an X2 interface). In another embodiment, the eNode B can send the common BSR message to each of the eNode B 120 and the eNode B 130 separately.

In another configuration, the dual connectivity UE 110 can send different BSR messages to a plurality of different eNode Bs, such as eNode B 120 and eNode B 130. In one embodiment, the UE can send a first BSR message dedicated to the eNode B 120 and a second BSR message dedicated to the eNode B 130. In one example, when a total BSR is 100 bytes (BSR_Total), the dual connectivity UE 110 can send a first BSR message with a 40 byte request (BSR_MeNode B) to the eNode B 120 (such as an MeNode B) and a second BSR message with a 60 byte request (BSR_SeNode B) to the eNode B 130 (such as an SeNode B).

One advantage of sending separate BSR information from the dual connectivity UE 110 in a common BSR message or separate BSR messages is to indicate to the eNode Bs 120 and 130 an uplink scheduling preferences of the dual connectivity UE 110. Another advantage of sending separate BSR information from the dual connectivity UE 110 in a common BSR message or separate BSR messages is to provide a more granular or detailed BSRs than a total BSR size message.

FIG. 2 depicts a flowchart 200 to illustrate the functionality of one embodiment of the circuitry with a UE operable to determine when to send a BSR to one eNode B or a plurality of eNode Bs. The functionality can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The circuitry can be configured to connect to both an MeNode B and an SeNode B, as in block 210. The circuitry can be further configured to determine whether to send the BSR to one of the MeNode B or the SeNode B or both the MeNode B and the SeNode B, as in block 220. In one configuration, the UE can determine when to send a common BSR or separate BSRs to one or more eNode Bs (as in FIG. 1) based on a bearer split configuration of the communications network. In one embodiment, the bearer split configurations can include: a no UL bearer split configuration, a no UL bearer split and a RLC status PDU transmitted to a corresponding eNode B configuration, and a UL bearer split configuration.

When the circuitry determines to send the BSR to both the MeNode B and the SeNode B, the circuitry can also be configured to send a BSRs to both the MeNode B and the SeNode B for UL resource grants, as in block 230. When the circuitry determines not to send the BSR to both the MeNode B and the SeNode B, the circuitry can also be configured to select an MeNode B or an SeNode B to send a BSR, as in block 240. In one embodiment, the UE can select the MeNode B or the SeNode B to send the BSR based on a predetermined rule or criteria. When the circuitry selects the SeNode B, the circuitry can be further configured to send a BSR to the SeNode B for a UL resource grant at the SeNode B, as in block 250. When the circuitry selects the MeNode B, the circuitry can be further configured to send a BSR to the MeNode B for a UL resource grant at the SeNode B, as in block 260.

In one example, for a communications network with DL bearer split and no UL bearer split configuration, the UE can send a BSR to an eNode B with a bearer that corresponds to the eNode B. In this example, the UE can communicate a buffer size to the eNode B using a BSR medium access control (MAC) control element (CE) of the associated eNode B.

In another embodiment, the communications network can have DL bearer split with no UL bearer split and transmit a radio link control (RLC) status protocol data unit (PDU) to the eNode B with no UL bearer configuration for the corresponding UE. In one example, an alternative architecture, e.g. an architecture with bearer split, can be used where a downlink (DL) bearer splitting and an UL bearer split has not been undetermined (e.g. not split).

In one embodiment, when the DL bearer is split and the UL bearer is not split, one or more RLC Status PDUs can be sent to the corresponding eNode Bs. In another example, separate BSR information can be sent to an MeNode B and an SeNode B. In another example, a BSR size can be sent to one of the MeNode B or the SeNode B and a BSR requesting UL resource allocation for a size of a RLC Status PDU can be sent to another of the MeNode B or the SeNode.

In one embodiment, when the BSR is communicated via a UL bearer of the SeNode B, a BSR for the MeNode B can be a size of the RLC Status PDUs and a BSR for the SeNode B can be a total BSR size. In another embodiment, when the BSR is communicated via a UL bearer of the MeNode B, a BSR for the SeNode B can be a size of the RLC Status PDUs and a BSR for the MeNode B can be a total BSR size. In another embodiment, a total BSR can be sent to one of the MeNode B or the SeNode B and the one of the MeNode B or the SeNode B can communicate the total BSR to another of the MeNode B or the SeNode B over an Xn interface to indicate UL resource allocation for a RLC Status PDU.

In one configuration, the communications network can have a UL bearer split architecture. In one embodiment, the UE can send a BSR to one of an MeNode B or an SeNode B and the one of the MeNode B or the SeNode B can communicate the BSR over an Xn interface to another of the MeNode B or the SeNode B. In one example, the UE can send the BSR to the MeNode B and the MeNode B can communicate with the SeNode B to send and/or receive the BSR information along with loading information and a channel quality indicator (COI), as shown in FIG. 1. In one embodiment, the MeNode B can communicate the BSR information via an Xn interface.

One advantage of sending the BSR message to one of the MeNode B or the SeNode B is to minimize signaling overhead and reduce usage of radio resources for a UE to communicate the BSR information to a plurality of eNode Bs. In another embodiment, the UE can send a BSR to both the MeNode B and the SeNode B. One advantage of sending the BSR to both the MeNode B and the SeNode B is to increase a robustness or diversity of the BSR information.

In one embodiment, BSR information can include a total BSR (BSR_Total) of a BSR for the MeNode B and a BSR for the SeNode B. In one example, the BSR_Total=X+Y, where X is the BSR for the MeNode B and Y is the BSR for the SeNode B. In another embodiment, a BSR MAC CE can be used to communicate separate BSR_Total messages to the MeNode B and the SeNode B. In another example, to avoid a redundancy in communicating BSR message to the MeNode B and the SeNode B and avoid allocating excessive UL resources for a UE, the MeNode B and the SeNode B can coordinate, over an Xn interface, UL resource grants for the UE from the MeNode B and from the SeNode B.

In one embodiment, BSR information can include a selected BSR MAC CE. In one example, the selected BSR MAC CE can include one or more data fields for a BSR for the MeNode B (e.g. BSR_MeNode B=X) and one or more data fields for a BSR for the SeNode B (e.g. BSR_SeNode B=Y).

FIGS. 3, 4, and 5 show different configurations of the selected BSR MAC CE. In another embodiment, the selected BSR MAC CE can include one or more separate data fields for buffer size information for the MeNode B and/or the SeNode B. Previously, BSR MAC CEs have only included data fields for a single eNode B. However, this cannot be used in the use of an MeNode B and an SeNode B. Accordingly, new dual BSR MAC CEs can be used that include data fields for two eNode Bs.

As used herein, the term “dual” is intended to refer to a BSR MAC CE that includes data fields for at least two eNode Bs. A BSR MAC CE that is sent to one or both of an MeNode B or an SeNode B can be a dual BSR MAC CE that includes data fields for both the MeNode B and SeNode B. The data fields can include buffer size information for both the MeNode B and SeNode B. Additional information for the multiple eNode Bs may also be included in the dual BSR MAC CE.

FIG. 3A depicts a dual short BSR 300 with a truncated BSR MAC CE. In one embodiment, the dual short BSR can include: a logic channel group (LCG) identification (ID), an MeNode B buffer size; an SeNode B buffer size; and a reserve bit (R). In one embodiment, the dual short BSR can be used when the BSR includes a data field for a total buffer size for the MeNode B and a total buffer size for the SeNode B. In one embodiment, a logical channel identification (LCID) from a reserved LCID pool, such as a pool from 01011-11000, for uplink shared channel (UL-SCH) can be used to identify the dual short BSR.

FIG. 3B depicts a dual long BSR 310 with a full BSR MAC CE. In one embodiment, the dual short BSR can include a plurality of MeNode B buffer sizes (such as MeNode B buffer sizes 0-3) and a plurality of SeNode B buffer sizes (such as SeNode B buffer sizes 0-3). In one embodiment, the dual long BSR can include separate data fields for different buffer sizes of the MeNode B and different buffer sizes of the SeNode B. An LCID from a reserved LCID pool, such as a pool from 01011-11000, for UL-SCH can be used to identify the dual long BSR.

FIG. 4 illustrates an R/R/E/LCID MAC subheader 400. In one embodiment, the R/R/E/LCID MAC subheader can include: reserve bits (R); an extension bit (E), and LCID bits. In one embodiment, the reserved bits (R) of the R/R/E/LCID MAC subheader can correspond to a BSR MAC CE that can be used to identify a legacy BSR, a dual short BSR, or a dual long BSR. FIG. 4 further shows two reserved bits (RR) in the MAC CE R/R/E/LCID subheader. The reserved bits RR can be used to identify legacy and dual BSR MAC CEs. The identification by the reserved bits RR can allow for the use of a single LCID for these BSR MAC CEs as well. In one example, RR=00 can represent a legacy BSR MAC CE and RR=11 can represent a dual long MAC CE or a dual short MAC CE.

In one embodiment, the UE can send a selected BSR MAC CE, such as a dual BSR MAC CE, to one of the MeNode B or the SeNode B. In another embodiment, the UE can send the selected BSR MAC CE to both the MeNode B and the SeNode B. In one example, when the UE sends the selected BSR MAC CE to one of the MeNode B or the SeNode B, the receiving eNode B can communicate the information to an other of the MeNode B or the SeNode via an Xn interface. One advantage of the UE sending the selected BSR MAC CE to one of the MeNode B or the SeNode B is to eliminate a redundancy in UL grant requests.

In one embodiment, a first BSR MAC CE can include a BSR for the MeNode B and a second BSR MAC CE can include a BSR for the SeNode B. In one example, the UE can communicate the first BSR MAC CE to the MeNode B and communicate the second BSR MAC CE to the SeNode B. In one embodiment, the first BSR MAC CE and/or the second BSR MAC CE can be a legacy BSR MAC CE message, where a buffer size in the first BSR MAC CE or second BSR MAC CE is associated with a link between the UE and the respective eNode B.

Another example provides functionality 500 of circuitry of a UE operable to communicate buffer status report (BSR) information to an evolved node B (eNode B), as shown in the flow chart in FIG. 5. The functionality may be implemented as a method or the functionality may be executed as instructions on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The circuitry can be configured to buffer data at the UE for communication to at least one of a master eNode B (MeNode B) or a secondary eNode B (SeNode B), as in block 510. The circuitry can be further configured to determine BSR information based on the buffered data at the UE, as in block 520. The circuitry can be further configured to determine an uplink split configuration of the UE for the MeNode B and the SeNode B, as in block 530. The circuitry can be further configured to identify the MeNode B or the SeNode B based on the uplink split configuration to send selected BSR information, as in block 540. The circuitry can be further configured to communicate the selected BSR information to the identified MeNode B or the selected SeNode B, as in block 550.

In one embodiment, the circuitry can be further configured to identify an other of the MeNode B or the SeNode B based on the uplink split configuration to send selected BSR information and communicate the selected BSR information to the identified other MeNode B or the identified other SeNode B. In another embodiment, the uplink split configuration includes: a no uplink split configuration for the MeNode B and the SeNode B; a no uplink split configuration with a radio link control (RLC) status protocol data unit (PDU) communicated to the MeNode B or the SeNode B; and an uplink split configuration for the MeNode B and the SeNode B. In another embodiment, the circuitry can be further configured to determine that the uplink split configuration is the no uplink split configuration with the RLC status PDU communicated to the MeNode B or the SeNode B, select one of the MeNode B or the SeNode B to communicate a size of RLC status PDU at the UE, and select an other of the MeNode B or the SeNode B to communicate a size of the total buffered data at the UE.

In one configuration, the circuitry can be further configured to determine that the uplink split configuration is the no uplink split configuration with the RLC status PDU communicated to the MeNode B or the SeNode B, select one of the MeNode B or the SeNode B to communicate a size of the total buffered data at the UE, and communicate the size of the total buffered data at the UE to the selected MeNode B or the selected SeNode B. In another configuration, the circuitry can be further configured to determine that the uplink split configuration is the uplink split configuration for the MeNode B and the SeNode B and communicate a total BSR to each of the MeNode B and the SeNode B, wherein the total BSR includes a total of an uplink data buffer size at the UE for the MeNode B and an uplink data buffer size at the UE for the SeNode B.

In one example, the circuitry can be further configured to determine that the uplink split configuration is the uplink split configuration for the MeNode B and the SeNode B, select one of the MeNode B or the SeNode B to communicate a BSR medium access control (MAC) control element (CE) message, and communicate the BSR MAC CE message to the selected MeNode B or the selected SeNode B. In another example, the BSR MAC CE message includes one or more fields for one or more uplink data buffer sizes at the UE for the MeNode B and one or more fields for one or more uplink data buffer sizes at the UE for the SeNode B. In another example, the circuitry can be further configured to communicate the BSR MAC CE message to the remaining MeNode B or the remaining SeNode B. In another example, the circuitry can be further configured to determine that the uplink split configuration is the uplink split configuration for the MeNode B and the SeNode B; communicate a first BSR MAC CE message to the MeNode B, wherein the first BSR MAC CE includes an uplink data buffer size for the MeNode B at the UE; and communicate a second BSR MAC CE to the SeNode B, wherein the second BSR MAC CE includes an uplink data buffer size for the SeNode B at the UE.

Another example provides functionality 600 of circuitry of an eNode B operable to communicate a buffer status report (BSR) to another eNode B, as shown in the flow chart in FIG. 6. The functionality may be implemented as a method or the functionality may be executed as instructions on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The circuitry can be configured to determine an uplink split configuration of the UE, as in block 610. The circuitry can be further configured to receive BSR information from the UE, as in block 620. The circuitry can be further configured to allocate an uplink (UL) resource grant for the UE based on the BSR information, as in block 630. The circuitry can be further configured to communicate at least a portion of the BSR information to the other eNode B based on the uplink split configuration, as in block 640.

In one embodiment, the circuitry can be further configured to communicate the BSR information to the other eNode B using an Xn interface. In another embodiment, the eNode B and the other eNode B each have a MAC scheduler for UL resource grants for the UE. In another embodiment, the circuitry can be further configured to calculate an UL resource grant for the eNode B based, at least in part, on the BSR information. In another embodiment, the circuitry can be further configured to calculate an UL resource grant for the eNode B based, at least in part, on the BSR information. In another embodiment, the circuitry can be further configured to communicate selected BSR information with the other eNode B using an Xn interface and coordinate UL resource grants of the eNode B and the other eNode B for the UE based on the selected BSR information. In another embodiment, the circuitry can be further configured to communicate loading information and a channel quality indicator (CQI) to the other eNode B using an Xn interface.

Another example provides functionality 700 of product including a non-transitory storage medium having stored thereon instructions that are adapted to be executed to implement a method of directing buffer status report (BSR) information to an evolved node B (eNode B), as in the flow chart in FIG. 7. The instructions of the product can be implemented as a method or as instructions on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The method can comprise buffering data at the UE for communication to a first eNode B and a second eNode B, as in block 710. The method can further comprise determining BSR information based on the buffered data at the UE, as in block 720. The method can further comprise determining an uplink split configuration of the UE for the first eNode B and the second eNode B, as in block 730. The method can further comprise identifying the first eNode B or the second eNode B based on the uplink (UL) split configuration to send selected BSR information, as in block 740.

In one embodiment, the first eNode B is a Master eNode B (MeNode B) and the second eNode B is a secondary eNode B (SeNode B). In another embodiment, the method can further comprise communicating the selected BSR information to the identified first eNode B or the identified second eNode B. In another embodiment, the method can further comprise selecting the MeNode B or the SeNode B using a predetermined rule. In another embodiment, the method can further comprise sending the selected BSR information to the identified first eNode B or the identified second eNode B to request an UL resource grant at the selected MeNode B or the selected SeNode B for the buffered data. In another embodiment, the method can further comprises sending the selected BSR information to the identified first eNode B and the identified second eNode B to request an UL resource grant at the selected MeNode B and an other UL resource grant the selected SeNode B for the buffered data. In another embodiment, the BSR information includes one or more of: a size of radio link control (RLC) buffers at the UE; a size of packet data convergence protocol (PDCP) buffers at the UE; a size of the total buffered data at the UE; an uplink data buffer size for the first eNode B at the UE; and an uplink data buffer size for the second eNode B at the UE.

In one example, the method can further comprise communicating selected BSR information to the first eNode B and communicate other selected BSR information to the second eNode B. In another example, the method can further comprise the selected BSR information includes a size of radio link control (RLC) buffers at the UE and the other selected BSR information includes size of packet data convergence protocol (PDCP) buffers at the UE. In another example, the method can further comprise communicating, to the first eNode B, a BSR message associated with a bearer of the first eNode B and communicating, to the second eNode B, a BSR message associated with a bearer of the second eNode B.

FIG. 8 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device. The wireless device can include one or more antennas configured to communicate with a node or transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), a remote radio unit (RRU), a central processing module (CPM), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and Wi-Fi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN.

FIG. 8 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device. The display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities. A non-volatile memory port can also be used to provide data input/output options to a user. The non-volatile memory port can also be used to expand the memory capabilities of the wireless device. A keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard can also be provided using the touch screen.

Various techniques, or certain aspects or portions thereof, can take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, the computing device can include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements can be a RAM, EPROM, flash drive, optical drive, magnetic hard drive, or other medium for storing electronic data. The base station and mobile station can also include a transceiver module, a counter module, a processing module, and/or a clock module or timer module. One or more programs that can implement or utilize the various techniques described herein can use an application programming interface (API), reusable controls, and the like. Such programs can be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language can be a compiled or interpreted language, and combined with hardware implementations.

It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules can also be implemented in software for execution by various types of processors. An identified module of executable code can, for instance, comprise one or more physical or logical blocks of computer instructions, which can, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but can comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of executable code can be a single instruction, or many instructions, and can even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data can be identified and illustrated herein within modules, and can be embodied in any suitable form and organized within any suitable type of data structure. The operational data can be collected as a single data set, or can be distributed over different locations including over different storage devices, and can exist, at least partially, merely as electronic signals on a system or network. The modules can be passive or active, including agents operable to perform desired functions.

Reference throughout this specification to “an example” means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in an example” in various places throughout this specification are not necessarily all referring to the same embodiment.

As used herein, a plurality of items, structural elements, compositional elements, and/or materials can be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present invention can be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present invention.

Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.

While the forgoing examples are illustrative of the principles of the present invention in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the invention. Accordingly, it is not intended that the invention be limited, except as by the claims set forth below. 

What is claimed is:
 1. A user equipment (UE) operable to communicate buffer status report (BSR) information to an evolved node B (eNode B), the UE having circuitry configured to: buffer data at the UE for communication to at least one of a master eNode B (MeNode B) or a secondary eNode B (SeNode B); determine BSR information based on the buffered data at the UE; determine an uplink split configuration of the UE for the MeNode B and the SeNode B; identify the MeNode B or the SeNode B based on the uplink split configuration to send selected BSR information; and communicate the selected BSR information to the identified MeNode B or the selected SeNode B.
 2. The circuitry of claim 1, further configured to: identify an other of the MeNode B or the SeNode B based on the uplink split configuration to send selected BSR information; and communicate the selected BSR information to the identified other MeNode B or the identified other SeNode B.
 3. The circuitry of claim 1, wherein the uplink split configuration includes: a no uplink split configuration for the MeNode B and the SeNode B; a no uplink split configuration with an radio link control (RLC) status protocol data unit (PDU) communicated to the MeNode B or the SeNode B; and an uplink split configuration for the MeNode B and the SeNode B.
 4. The circuitry of claim 2, further configured to: determine that the uplink split configuration is the no uplink split configuration with the RLC status PDU communicated to the MeNode B or the SeNode B; select one of the MeNode B or the SeNode B to communicate a size of RLC status PDU at the UE; and select an other of the MeNode B or the SeNode B to communicate a size of the total buffered data at the UE.
 5. The circuitry of claim 2, further configured to: determine that the uplink split configuration is the no uplink split configuration with the RLC status PDU communicated to the MeNode B or the SeNode B; select one of the MeNode B or the SeNode B to communicate a size of the total buffered data at the UE; and communicate the size of the total buffered data at the UE to the selected MeNode B or the selected SeNode B.
 6. The circuitry of claim 2, further configured to: determine that the uplink split configuration is the uplink split configuration for the MeNode B and the SeNode B; and communicate a total BSR to each of the MeNode B and the SeNode B, wherein the total BSR includes a total of an uplink data buffer size at the UE for the MeNode B and an uplink data buffer size at the UE for the SeNode B.
 7. The circuitry of claim 2, further configured to: determine that the uplink split configuration is the uplink split configuration for the MeNode B and the SeNode B; select one of the MeNode B or the SeNode B to communicate a dual BSR medium access control (MAC) control element (CE) message; and communicate the dual BSR MAC CE message to the selected MeNode B or the selected SeNode B.
 8. The circuitry of claim 7, wherein the dual BSR MAC CE message includes one or more fields for one or more uplink data buffer sizes at the UE for the MeNode B and one or more fields for one or more uplink data buffer sizes at the UE for the SeNode B.
 9. The circuitry of claim 7, further configured to communicate the dual BSR MAC CE message to the remaining MeNode B or the remaining SeNode B.
 10. The circuitry of claim 2, further configured to: determine that the uplink split configuration is the uplink split configuration for the MeNode B and the SeNode B; communicate a first BSR MAC CE message to the MeNode B, wherein the first BSR MAC CE includes an uplink data buffer size for the MeNode B at the UE; and communicate a second BSR MAC CE to the SeNode B, wherein the second BSR MAC CE includes an uplink data buffer size for the SeNode B at the UE.
 11. An evolved node B (eNode B) operable to communicate a buffer status report (BSR) to an other eNode B, the eNode B having circuitry configured to: determine an uplink split configuration of the UE; receive BSR information from the UE; allocate an uplink (UL) resource grant for the UE based on the BSR information; and communicate at least a portion of the BSR information to the other eNode B based on the uplink split configuration.
 12. The circuitry of claim 11, further configured to communicate the BSR information to the other eNode B using an Xn interface.
 13. The circuitry of claim 11, wherein the eNode B and the other eNode B each have a MAC scheduler for UL resource grants for the UE.
 14. The circuitry of claim 11, further configured to calculate an UL resource grant for the eNode B based, at least in part, on the BSR information.
 15. The circuitry of claim 11, further configured to: communicate selected BSR information with the other eNode B using an Xn interface; and coordinate UL resource grants of the eNode B and the other eNode B for the UE based on the selected BSR information.
 16. The circuitry of claim 11, further configured to communicate loading information and a channel quality indicator (CQI) to the other eNode B using an Xn interface.
 17. A product including a non-transitory storage medium having stored thereon instructions that are adapted to be executed to implement a method of directing buffer status report (BSR) information to an evolved node B (eNode B), the method comprising: buffering data at the UE for communication to a first eNode B and a second eNode B; determining BSR information based on the buffered data at the UE; determining an uplink split configuration of the UE for the first eNode B and the second eNode B; and identifying the first eNode B or the second eNode B based on the uplink (UL) split configuration to send selected BSR information.
 18. The product of claim 17, wherein the first eNode B is a Master eNode B (MeNode B) and the second eNode B is a secondary eNode B (SeNode B).
 19. The product of claim 17, wherein the method further comprises communicating the selected BSR information to the identified first eNode B or the identified second eNode B.
 20. The product of claim 17, wherein the method further comprises selecting the MeNode B or the SeNode B using a predetermined rule.
 21. The product of claim 17, wherein the method further comprises sending the selected BSR information to the identified first eNode B or the identified second eNode B to request an UL resource grant at the selected MeNode B or the selected SeNode B for the buffered data.
 22. The product of claim 17, wherein the method further comprises sending the selected BSR information to the identified first eNode B and the identified second eNode B to request an UL resource grant at the selected MeNode B and an other UL resource grant the selected SeNode B for the buffered data.
 23. The product of claim 17, wherein the BSR information includes one or more of: a size of radio link control (RLC) buffers at the UE; a size of packet data convergence protocol (PDCP) buffers at the UE; a size of the total buffered data at the UE; an uplink data buffer size for the first eNode B at the UE; and an uplink data buffer size for the second eNode B at the UE.
 24. The product of claim 17, wherein the method further comprises communicating selected BSR information to the first eNode B and communicate other selected BSR information to the second eNode B.
 25. The product of claim 24, wherein the selected BSR information includes a size of radio link control (RLC) buffers at the UE and the other selected BSR information includes size of packet data convergence protocol (PDCP) buffers at the UE.
 26. The product of claim 17, wherein the method further comprises: communicating, to the first eNode B, a BSR message associated with a bearer of the first eNode B; and communicating, to the second eNode B, a BSR message associated with a bearer of the second eNode B. 